Skip to content

Add support for FTS5#17

Merged
rkistner merged 1 commit intojourneyapps:masterfrom
fholzer:support-fts5
Mar 27, 2019
Merged

Add support for FTS5#17
rkistner merged 1 commit intojourneyapps:masterfrom
fholzer:support-fts5

Conversation

@fholzer
Copy link
Copy Markdown
Contributor

@fholzer fholzer commented Feb 23, 2019

Adds support for FTS5, and a unit test to check if it actually works.

Cheers,
Ferdinand

@fholzer
Copy link
Copy Markdown
Contributor Author

fholzer commented Mar 19, 2019

@rkistner rkistner merged commit 2998fbe into journeyapps:master Mar 27, 2019
grebe added a commit to grebe/Signal-Desktop that referenced this pull request Feb 3, 2020
Signal is currently using a forked version of node-sqlcipher. I'm not
entirely sure as to all the motivations for forking, but it seems that
one reason may have been because upstream didn't support FTS5. This
reason is no longer relevant because of this PR [^1], which adds FTS5
support upstream.

Another reason for the forked version of node-sqlcipher may be to bundle
libcrypto. This is causing problems with many Linux users, especially
those who are not using Ubuntu [^2][^3]. It seems to me that statically
linking is not generally considered to be a best practice on Linux. The
upstream project's README [^4] seems to have a sensible policy: bundling
OpenSSL on Windows and OS X platforms and dynamically linking to the
system's library on Linux platforms.

This PR moves away from the forked node-sqlcipher and returns back to
upstream. This seems to fix OpenSSL problems on non-Ubuntu Linux
distributions.

[^1]: journeyapps/node-sqlcipher#17
[^2]: signalapp#2634
[^3]: signalapp#2662
[^4]: https://github.com/journeyapps/node-sqlcipher#openssl
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants